Could you restructure this into a sequence of individual steps? See for example the Multinode page which goes through a few things step-by-step

This seems a little unnecessary for this because it would end up being 2 steps; this is more to make people aware of the various configs which could snag the deployment.

I think at the moment it misses a few important steps, in particular "It of course goes without saying that the network should exist in networks.yml" is a pretty big thing to gloss over.

So for example you could have:

1. Where to enable the service in kolla.yml
2. How to define the octavia network in networks.yml
3. How to define network interfaces for controllers
4. What to check for neutron provider networks
5. How to select the right driver(s), and the differences between Amphora vs OVN
6. How to properly configure the Amphora driver

Please also keep in mind that simple, clear instructions make for the best docs. try to stay away from wordyness.

For example:

Much like any other Kolla managed service, the method of deploying Octavia is as simple
as ...

could be written as:

To enable Octavia, set ...

I have an idea on how to make a nice comprehensive list. Regarding the wordyness, in some cases it is intentional, in the example provided mentioning its similarity to other Kolla managed services will give users a lot of context as to what to expect, as long as they have deployed at least one service before; in addition to reinforcing the steps for deploying services. In other cases, I agree and some sentences are wordy without adding anything.